Update sentry-rust monorepo to 0.48.0 - #8715

v0.48.3

Compare Source

The Sentry Rust SDK now reports data discarded by the SDK to Sentry’s Stats page. The SDK reports approximate counts for drops from transports, queues, rate-limit backoff, sampling, event processors, and before_send* callbacks, including span counts for dropped transactions and byte counts for dropped logs and metrics.

New Features

• Added EnvelopeFilter and EnvelopeFilterCallbacks, which let callers observe envelope items removed by Envelope::filter, including attachments removed after their event or transaction is filtered out. Existing Envelope::filter closure callers continue to work, although some closures may require an explicit item type annotation (#​1182).
• Added the LossSource trait, which provides the client report data categories and quantities to report when supported Sentry data is dropped (#​1170).
• Added TransportFactory::create_transport_with_options, which constructs transports from TransportOptions instead of full ClientOptions (#​1142).
• Added transport-specific options types and with_options constructors for built-in HTTP transports, including ReqwestHttpTransportOptions, CurlHttpTransportOptions, UreqHttpTransportOptions, and EmbeddedSVCHttpTransportOptions (#​1142).
• Added transport worker options types and deprecated the legacy constructors for built-in background transport workers, including StdTransportThreadOptions and TokioTransportThreadOptions (#​1142).
• Added client report protocol types in sentry-types, including ClientReport, client_report::Item, client_report::Category, and client_report::Reason, plus support for serializing client_report envelope items (#​1144).
• Added a client report Recorder type, which modern TransportFactory implementations receive via TransportOptions. Transports can use this recorder to record discarded Sentry data; the SDK aggregates these reported losses and automatically sends them in a future envelope (#​1158).

Deprecations

• Deprecated Hub::with. Use Hub::current instead (#​1126).

Fixes

• Fixed ureq transport handling for HTTP error statuses so 429 rate limits and 413 payload-too-large responses are processed correctly (#​1177).

Behavior Changes

• Custom transport factories that implement TransportFactory::create_transport now receive ClientOptions reconstructed from TransportOptions. The reconstructed options include only transport-relevant fields, such as DSN, user agent, proxy settings, and TLS certificate validation settings. This may affect code that reads non-transport fields in create_transport, but the API remains source-compatible and this change is included in a minor/patch release (#​1142).

v0.48.2

Compare Source

New Features

• Added rustls-no-provider feature flag in the sentry crate to allow using the rustls transport with a different crypto provider (#​1103).

Fixes

• Serialize attachment envelope headers as JSON to correctly encode header values (#​1109).
• Use checked arithmetic to handle possible overflows (#​1119, #​1121, #​1122).

v0.48.1

Compare Source

Fixes

• Changed ClientOptions::enable_metrics to default to true, aligning metrics behavior with other Sentry SDKs (#​1106). Metric capture APIs still require the metrics feature flag at compile time.

v0.48.0

Compare Source

Breaking Changes

• Added the following metrics-related fields to the ClientOptions struct in sentry-core. Both fields are no-ops, unless the metrics feature flag is enabled:
  • enable_metrics, used to enable sending metrics to Sentry (#​1073).
  • before_send_metric, used to define a callback for filtering/pre-processing metrics before sending to Sentry (#​1064).
• There are several breakages related to the SemVer feature additivity bug fixes:
  • sentry_core::ClientOptions fields before_send_log, enable_logs, auto_session_tracking, and session_mode are no longer gated behind the logs and release-health feature flags (#​1091). Code that constructs ClientOptions with a full struct literal (without ..Default::default()), or which exhaustively matches against it, must now include all four fields regardless of enabled features.
  • sentry_core::Scope can no longer be publicly constructed or exhaustively matched against, even when the client feature is disabled (#​1094). Previously, both of these were possible when client was disabled.
  • sentry_core::Scope::add_event_processor now requires passed closures to be RefUnwindSafe (#​1093). Thanks to this change, sentry_core::Scope is now UnwindSafe regardless of feature flag configuration; previously, Scope was only UnwindSafe when the client feature was disabled.
  • sentry_tracing::EventMapping is now #[non_exhaustive] (#​1097).
  • sentry_log::RecordMapping is now #[non_exhaustive] (#​1098).

New Features

📊📈💯 The Sentry-Rust SDK now supports emitting Sentry Metrics (#​1073)!

To get started, you will need to add the metrics feature flag when compiling the sentry crate. You will also need to enable metrics when initializing the SDK, like so:

use sentry::ClientOptions;

let _guard = sentry::init((
    "(your DSN here)",
    ClientOptions {
        enable_metrics: true,
        // ... other options ...
        ..Default::default()
    },
));

You can then capture metrics as follows:

use sentry::metrics;
use sentry::types::protocol::latest::Unit;

// We support counter, gauge, and distribution metrics.
metrics::counter("example.counter", 1).capture();
metrics::gauge("connections", 20).capture();
metrics::distribution("response.time", 123.4)
    .unit(Unit::Millisecond) // units can also be set on gauges
    .attribute("http.status", 200) // attributes can be set on all metric types
    .capture();

Fixes

• Fixed several feature additivity SemVer violations, where enabling a feature flag could have introduced breaking changes. All known violations are fixed now, so simply enabling an additional feature flag in any Sentry SDK crate should no longer cause any public API breakages. Fixing these issues required us to break the public API in some places; those breakages are detailed above.